home *** CD-ROM | disk | FTP | other *** search
- Path: news.ios.com!usenet
- From: vlad@gramercy.ios.com (vlad)
- Newsgroups: comp.lang.c++
- Subject: Re: Compiling OWL under Visual C++
- Date: Sat, 20 Jan 1996 00:46:25 GMT
- Organization: Internet Online Services
- Message-ID: <4dpdqc$1oc@news.ios.com>
- References: <1996Jan8.130134.12002@es.dupont.com>
- NNTP-Posting-Host: ppp-41.ts-7.hck.idt.net
- X-Newsreader: Forte Free Agent 1.0.82
-
- Malcolm Smart <MALCOLM.SMART@CONOCO.DUPONT.COM> wrote:
-
- >I know it's a specific compiler question rather than a C++ question, but
- >where else could I post it to reach the audience that attends this
- >Newsgroup?
-
- >--
-
- >Is it possible to take existing Borland OWL code, throw it into the VC++
- >IDE, compile and run it without modification? I already use OWL and want
- >to jump ship to Visual C++ && MFC and I'm hoping I can support my
- >existing code under the new environment.
-
- I wonder why would you like to do it. Either you are happy with
- Borland C++, which is really good, and use a framework called OWL or
- you think you would be more happy with Visual C++, which uses a
- framework called MFC. Those two frameworks are not compatible due to
- design philosophy and also you need to use DLLs for runtime support
- for your stuff.
-
- But there is a solution for your desires: get source code for all your
- DLL that contains OWL, recompile it, wait for compile error messages,
- modify DLL code, compile it, wait for compile messages and maybe it
- will work. I would not even attempt to do it.
-
- If you code is really carefully written, you can easily separate your
- application (domain model) code from OWL and then easily generate new
- MFC code that will replace your OWL code. It will be faster and safer.
-
-
-
-
-
- *******************************************
- * Vlastimil Adamovsky *
- * Smalltalk and C++ development *
- *******************************************
-
-